Methods, apparatuses, and systems for human machine interface (hmi) operations

ABSTRACT

Methods, apparatuses, systems, and implementations of an HMI control system for BOP rigs are disclosed. At least some versions of the disclosed systems enable a user to configure interface settings, perform actions on a BOP stack, view diagnostics, perform testing, and observe and rectify alarms. The disclosed systems may enable a user to more efficiently navigate between different interfaces and perform HMI functions due to a control zone configuration. Additionally, the control zone configuration may reduce operator error by assigning certain control zones to particular functions and requiring the user to take affirmative steps to perform destructive functions.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/449,447, filed Mar. 3, 2017, entitled “Methods, Apparatuses, andSystem for Human Machine Interface (HMI) Operations,” which claimspriority to U.S. Provisional Patent Applications 62/303,968 filed Mar.4, 2016 and 62/344,105 filed Jun. 1, 2016, each entitled “Methods,Apparatuses, and System for Human Machine Interface (HMI) Operations,”each of which is incorporated herein by reference in its entirety.

BACKGROUND 1. Field of the Invention

This disclosure relates generally to methods, apparatuses, and systemsthat can be used to provide a human machine interface (HMI) to control ahigh-reliability blow-out preventer (BOP) rig.

2. Description of Related Art

Operator error during operations of an HMI interface for a BOP rig cansignificantly contribute to system downtime and potentially increasesafety risk. This can happen due to outright operator error—for example,an operator operating the wrong component, or, more subtly, whenoperators are confronted with diagnosing several smaller problemsinstead of dealing with the root cause.

Fault tolerant and redundant systems are often hard for operators tounderstand and diagnose, at least in part because there can be multipleways to perform every function. One of the most important aspects tominimizing downtime risk associated with operator error is thesophistication of the master control software for the BOP rig. Themaster control system must be flexible to allow expert operators toselectively enable and disable such automatic failover to aid indiagnosing problems or operating in unusual situations. This complexitydoes not come without cost. This fault management approach requirescomplex software and increases the efforts in validation and testing.

To minimize such downtime, the HMI and control system has been designedwith certain guiding principles in mind. The overarching goal of theseprinciples is to make sure every design decision supports the operator'sability to operate safely, make good decisions, and to minimizedowntime.

SUMMARY

This disclosure includes embodiments of a computing system forimplementing a human machine interface (HMI) application. In someembodiments, the computing system may include a memory device and atleast one processor configured to enable the display of a graphical userinterface (GUI). The GUI may include one or more graphical elementsconfigured to implement, using the at least one processor, one or moresoftware applications stored on one or more servers. In someembodiments, the one or more software applications may be configured toinitiate a session of the HMI application by receiving a user input on auser interface running or stored on a hardware device comprising atleast one processor. In some embodiments, the one or more softwareapplications may enable the display of a plurality of non-overlappingzones that may include an action zone and one or more of a high-levelnavigation zone including one or more selectable navigation options anda system header zone. The one or more software applications may enablethe display of a plurality of selectable action options in the actionzone including a plurality of non-overlapping subzones. In someembodiments, the subzones may include an interface control subzone, aninformation subzone, and a system control subzone. The one or moresoftware applications may enable the display of one or more selectableaction options that may be displayed in predesignated subzones, whereinthe plurality of selectable action options may be modified based on aselection of the one or more selectable navigation options, wherein theselection may be one or more of a user selection and a defaultselection. In some embodiments, the one or more software applicationsmay receive, at the hardware device, data representing a user selectionof one of the one or more selectable action options, and may control anoperating state of one or more physical offshore drilling rig componentsbased on the user selection.

In some embodiments, the HMI application may be configured to implementone or more standard operating procedures applicable to one or moreoffshore drilling rigs. The HMI application may be further configured toreceive, at the hardware device, data representing one or moremodifications to the one or more standard operating procedures, applythe one or more modifications to the one or more standard operatingprocedures to create one or more modified standard operating procedures,and apply the one or more modified standard operating procedures to theone or more offshore drilling rigs. In some embodiments, the one or moreselectable navigation options may include one or more of a blowoutpreventer (BOP) stack control option, a diagnostics option, a testingoption, a settings option, an alarms option, a diverter option, asurface system option, an electronic riser angle option, and anemergency disconnect option.

In some embodiments, the one or more software applications may befurther configured to, after receiving a user selection of the BOP stackcontrol option, enable the display of a layout diagram that may includeone or more selectable components in the information subzone and mayrepresent a current stack arrangement of the one or more physicaloffshore drilling rig components. The one or more software applicationsmay be further configured to enable the display of one or more controloptions in the interface control subzone that may include one or morecontrol procedures and one or more destructive function control modes.

In some embodiments, the one or more software applications may befurther configured to enable the display of one or more visual statusdisplays in the system control subzone and, after receiving a userselection of one of the selectable components or control options, enablethe display of one or more function control options in the systemcontrol subzone. The one or more function control options may correspondto the user selection of one of the selectable components or controloptions.

In some embodiments, the one or more software applications may befurther configured to enable the display of a flowpath within the layoutdiagram and enable the display of one or more colors for the flowpath.One or more highlighted colors may correspond to one or more predictedflowpath states of the flowpath such as a predicted fluid flow state anda predicted fluid non-flow state. After receiving a user selection ofone of the selectable components or control options, the one or moresoftware applications may enable the display of one or more functioncontrol options in the system control subzone corresponding to the userselection of one of the selectable components or control options.

In some embodiments, the one or more software applications may befurther configured to receive a user input activating one or moredestructive function control modes, receive a user selection of one ormore destructive functions, enable the display of a destructive functionconfirmation option, and upon receipt of a user selection of thedestructive function confirmation option, perform one or more actions onone or more physical rig components corresponding to the selected one ormore destructive functions. In some embodiments, the one or moredestructive functions may include one or more of a pipe cutting actionand a BOP disconnect action.

In some embodiments, the one or more software applications may befurther configured to, after receiving a user selection of the settingsoption, enable the display of a drag-and-drop interface that may includeone or more component icons located in the interface control subzonethat may represent one or more physical rig components. The one or moresoftware applications may enable the display of metadata describing theone or more physical rig components.

In some embodiments, the one or more software applications may befurther configured to, after receiving a user selection of the at leastone component operation option, receive a user selection of the one ormore component icons. The one or more software applications may enable auser to drag the selected one or more component icons onto a layoutdiagram located in the information subzone that may represent a currentstack arrangement of the one or more physical rig components. Uponreceipt of the selected one or more component icons onto the layoutdiagram, the one or more software applications may modify the layoutdiagram and control a movement operation of the one or more physical rigcomponents into a modified current stack arrangement to match the one ormore component icons comprising the modified layout diagram.

In some embodiments, the one or more software applications may befurther configured to, after receiving a user selection of thediagnostics option, enable the display of one or more system diagnosticoptions in the interface control subzone. The one or more systemdiagnostic options may include one or more of a component diagnosticoption, a function diagnostic option, and an event diagnostic option.The one or more software applications may enable the display of one ormore control options in the system control subzone corresponding to theuser selection of one of the one or more system diagnostic options.

In some embodiments, the one or more software applications may befurther configured to, after receiving a user selection of the eventdiagnostic option, enable a display of an event timeline in theinformation subzone including a linear display of one or more eventscorresponding to one or more events logged by the HMI application andshowing a causal relationship between the one or more events and one ormore user actions. The one or more software applications may enable adisplay of an event log in the information subzone including a list ofthe one or more logged events. In some embodiments, the one or moresoftware applications may be further configured to enable a display of acomponent timeline in the information subzone including a linear displayof one or more component statuses corresponding to one or more componentstatus events logged by the HMI application. The one or more softwareapplications may enable a display of a component log in the informationsubzone including a list of the one or more logged component statusevents. In some embodiments, the one or more software applications maybe further configured to enable a display of a pressure and temperaturetimeline in the information subzone including a linear display of one ormore pressure and temperature statuses corresponding to one or morefluid flow status events logged by the HMI application. The one or moresoftware applications may enable a display of a pressure and temperaturelog in the information subzone including a list of the one or morelogged fluid flow status events.

In some embodiments, the one or more software applications may befurther configured to, after receiving a user selection of the testingoption, enable the display of one or more system testing type options inthe interface control subzone. The one or more system testing typeoptions may include one or more of a function testing option and apressure testing option. The one or more software applications mayenable the display of one or more test information fields in theinformation subzone including one or more of test status information andtest history information and, after receiving a user selection of one ofthe one or more system testing type options, enable the display of oneor more selectable test options. In some embodiments, the one or moresoftware applications may be further configured to, after receiving auser selection of one or more of the one or more selectable testoptions, perform one or more tests corresponding to the selected one ormore selectable test options and delay performing one or more testscorresponding to the unselected one or more selectable test options.

In some embodiments, the GUI may display the action zone in a centralportion of the GUI. The GUI may display the interface control subzone ona right side portion of the action zone, in a central portion of theaction zone, or on a left side portion of the action zone and mayinclude a single active interface window. In some embodiments, the HMIapplication may be further configured to enable a display of a colorpalette comprising a red color and a green color, display a red color toindicate one or more abnormal component states, and display a greencolor to indicate one or more of an error-free operating status and aphysical rig configuration having all rig components correctlyconfigured for a particular rig operation. The one or more events mayinclude one or more of a component failure and an alarm. In someembodiments, the GUI may include a touch screen interface configured toenable a user to select one of the one or more selectable navigationoptions and one of the one or more selectable action options by touchingan icon corresponding to the one or more selectable navigation optionsor the one or more selectable action options.

In some embodiments, the one or more software applications may befurther configured to, after receiving a user selection of thediagnostics option, enable the display of one or more system diagnosticoptions including one or more of a regulatory compliance option, anoperational status option, and an event log option. In some embodiments,the one or more software applications may be further configured to,after receiving a user selection of the regulatory compliance option,enable the display of a diagnostic decision path tree having one or morelevels, one or more nodes, and one or more pathways connecting the oneor more nodes, each of the one or more nodes having an icon representinga current diagnostic state of one or more rig components. The one ormore icons may show a first symbol to indicate one or more abnormalcomponent states and a second symbol to indicate one or more error-freecomponent states. The one or more levels may correspond to one or morerig components and the one or more nodes may correspond to one or morecomponent functions.

In some embodiments, the one or more rig components may comprise one ormore of an integrated manifold assembly, a regulator assembly, a commonrail, and a rigid conduit and hot line valve package. In someembodiments, the one or more software applications may be furtherconfigured to receive a user selection of a level from the one or morelevels, enable the display of one or more diagnostic detailscorresponding to the selected level, and enable the display of one ormore functions, each of the one or more functions corresponding to theone or more rig components represented by the selected level.

In some embodiments, a method of implementing a human machine interface(HMI) application may comprise initiating a session of the HMIapplication by receiving a user input on a user interface running orstored on a hardware device comprising at least one processor. Themethod may further comprise enabling the display of a plurality ofnon-overlapping zones including an action zone and one or more of ahigh-level navigation zone comprising one or more selectable navigationoptions and a system header zone. The method may further compriseenabling the display of a plurality of selectable action options in theaction zone. The action zone may include a plurality of non-overlappingsubzones having an interface control subzone, an information subzone,and a system control subzone. The method may further comprise enablingthe display of one or more selectable action options in predesignatedsubzones, wherein the plurality of selectable action options may bemodified based on a selection of the one or more selectable navigationoptions, wherein the selection is one or more of a user selection and adefault selection. The method may further comprise receiving, at thehardware device, data representing a user selection of one of the one ormore selectable action options and controlling an operating state of oneor more physical offshore drilling rig components based on the userselection.

In some embodiments, an apparatus for implementing a human machineinterface (HMI) application may include at least one processorconfigured to initiate a session of the HMI application by receiving auser input on a user interface running or stored on a hardware devicecomprising at least one processor. The at least one processor may befurther configured to receive a user input activating one or moredestructive function control modes, receive a user selection of one ormore destructive functions, enable the display of a destructive functionconfirmation option, and, upon receipt of a user selection of thedestructive function confirmation option, perform one or more actions onone or more physical offshore rig components corresponding to theselected one or more destructive functions.

The terms “a” and “an” are defined as one or more unless this disclosureexplicitly requires otherwise. The term “substantially” is defined aslargely but not necessarily wholly what is specified (and includes whatis specified; e.g., substantially 90 degrees includes 90 degrees andsubstantially parallel includes parallel), as understood by a person ofordinary skill in the art. In any disclosed embodiment, the terms“substantially,” “approximately,” and “about” may be substituted with“within [a percentage] of” what is specified, where the percentageincludes 0.1, 1, 5, and 10 percent.

The terms “comprise” (and any form of comprise, such as “comprises” and“comprising”), “have” (and any form of have, such as “has” and“having”), “include” (and any form of include, such as “includes” and“including”) and “contain” (and any form of contain, such as “contains”and “containing”) are open-ended linking verbs. As a result, a system,or a component of a system, that “comprises,” “has,” “includes” or“contains” one or more elements or features possesses those one or moreelements or features, but is not limited to possessing only thoseelements or features. Likewise, a method that “comprises,” “has,”“includes” or “contains” one or more steps possesses those one or moresteps, but is not limited to possessing only those one or more steps.Additionally, terms such as “first” and “second” are used only todifferentiate structures or features, and not to limit the differentstructures or features to a particular order.

Any embodiment of any of the disclosed methods, systems, systemcomponents, or method steps can consist of or consist essentiallyof—rather than comprise/include/contain/have—any of the describedelements, steps, and/or features. Thus, in any of the claims, the term“consisting of” or “consisting essentially of” can be substituted forany of the open-ended linking verbs recited above, in order to changethe scope of a given claim from what it would otherwise be using theopen-ended linking verb.

The feature or features of one embodiment may be applied to otherembodiments, even though not described or illustrated, unless expresslyprohibited by this disclosure or the nature of the embodiments.

The foregoing has outlined rather broadly certain features and technicaladvantages of embodiments of the present invention in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described below. It should beappreciated by those having ordinary skill in the art that theconception and specific embodiment disclosed may be readily utilized asa basis for modifying or designing other structures for carrying out thesame or similar purposes. It should also be realized by those havingordinary skill in the art that such equivalent constructions do notdepart from the spirit and scope of the invention as set forth in theappended claims. Additional features will be better understood from thefollowing description when considered in connection with theaccompanying figures. It is to be expressly understood, however, thateach of the figures is provided for the purpose of illustration anddescription only and is not intended to limit the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The following drawings illustrate by way of example and not limitation.For the sake of brevity and clarity, every feature of a given method orsystem is not always labeled in every figure related to that method orsystem. Identical reference numbers do not necessarily indicate anidentical feature. Rather, the same reference number may be used toindicate a similar feature or a feature with similar functionality, asmay non-identical reference numbers.

FIG. 1 illustrates an exemplary HMI method according to an embodiment ofthe disclosure.

FIG. 2 shows an embodiment of an exemplary user interface architecturehaving one or more well-defined zones or screen portions for displayingdifferent types of information and controls according to an embodimentof the HMI system.

FIG. 3A shows an embodiment of an exemplary GUI display exhibiting thethree zones of the screen architecture shown in FIG. 2 as applied to ablow-out preventer (BOP) Stack option according to an embodiment of theHMI system.

FIG. 3B shows an embodiment of an exemplary GUI display when a componentoption is selected according to an embodiment of the HMI system.

FIGS. 4A-4B shows an embodiment of an exemplary GUI display when aprocess control option is selected according to an embodiment of the HMIsystem.

FIG. 5 shows an embodiment of an exemplary GUI display when a userselects a Surface Systems option according to an embodiment of the HMIsystem.

FIG. 6 shows an embodiment of an exemplary GUI display when a userselects an Electronic Riser Angle option according to an embodiment ofthe HMI system.

FIG. 7 shows an embodiment of an exemplary GUI display when a userselects a Diverter option according to an embodiment of the HMI system.

FIG. 8A shows an embodiment of an exemplary GUI display when a userselects a Diagnostics option.

FIG. 8B shows an embodiment of an exemplary GUI display when a userselects a BOP Components option within the Diagnostics option accordingto an embodiment of the HMI system.

FIG. 8C shows an embodiment of an exemplary GUI display when a userselects a BOP Functions option within the Diagnostics option accordingto an embodiment of the HMI system.

FIG. 8D shows an embodiment of an exemplary GUI display when a userselects a regulatory compliance option according to an embodiment of theHMI system.

FIG. 9 shows an embodiment of an exemplary GUI display of a diagnosticevent log according to an embodiment of the HMI system.

FIG. 10 shows an embodiment of an exemplary GUI display of apressure/temperature log according to an embodiment of the HMI system.

FIG. 11 shows an embodiment of an exemplary GUI display of a BOPComponent log according to an embodiment of the HMI system.

FIG. 12 shows an embodiment of an exemplary GUI display when a userselects a Testing option according to an embodiment of the HMI system.

FIG. 13 shows an embodiment of an exemplary GUI display when a userselects a System Settings option according to an embodiment of the HMIsystem.

FIG. 14 shows an embodiment of an exemplary GUI display when a userselects an Alarms option according to an embodiment of the HMI system.

FIG. 15 shows an embodiment of an exemplary GUI display when a userselects an Emergency Disconnect Sequence (EDS) option according to anembodiment of the HMI system.

FIG. 16 shows an embodiment of an exemplary client-server interfaceaccording to an embodiment of the HMI system.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Referring now to the drawings, FIG. 1 illustrates an exemplary HMImethod 100 according to an embodiment of the disclosure. In theembodiment shown, method 100 may begin at step 110 by receiving a userinput to initiate an HMI session. In some embodiments, the system mayinitiate an HMI session when a user accesses a hardware device. In someembodiments, the hardware device may be connected to a network. Thehardware device may be a computer terminal located at an oil rig site ora computer terminal located remotely from an oil rig site. In someembodiments, the oil rig site may be an offshore site and the oil rigmay have one or more physical drilling components configured foroffshore drilling. In some embodiments, an offshore drilling oil rig mayhave BOP components. The hardware device may also be a mobile device.The hardware device may be configured to access one or more softwareapplications that perform HMI functionalities. The system may initializethe HMI session when a user accesses a user interface comprising thehardware device. The user interface is defined broadly and may comprisea client device that may access one or more applications stored on oneor more server devices. The user interface may also access one or moreapplications stored locally on the client device.

In the embodiment shown in FIG. 1, the system may continue method 100 atstep 120 by enabling the display of a plurality of selectable options tothe user. In some embodiments, the display comprises a graphical userinterface (GUI) enabling a user to view and interact with one or moredisplay elements on a screen. In some embodiments, the system may enablethe display by causing one or more processors configured for displayfunctionality to perform actions that implement the displayfunctionality. In some embodiments, the one or more processors mayexecute code or initiate one or more software applications thatimplement the display functionality. In some embodiments, the actionsperformed by the one or more processors may cause the plurality ofselectable options to be displayed to the user via a mobile deviceand/or computing device. In some embodiments, the selectable options maycomprise one or more categories relevant to operating an oil rig. Otherselectable options may comprise one or more elements comprising a logdisplay. These options may be displayed as one or more selectable iconslocated in a predefined portion of the screen and enable the user toeasily navigate between the one or more selectable options. The iconsmay represent the different selectable options available to the user. Inthe embodiment shown, the system may continue method 100 at step 130 byreceiving a user selection of one of the selectable options. In someembodiments, the user may make a selection by selecting an iconcorresponding to the category the user desires to access. The user mayselect elements displayed in the GUI via a keyboard, mouse, touchscreenor touchpad, or in any other suitable manner.

In the embodiment shown, the system at step 140 may enable the displayof one or more selectable components and/or processes at the mobiledevice and/or computing device based on the user selection made from theplurality of selectable options. In some embodiments, the selectablecomponents may be located in a predefined portion of the screendifferent than the selectable option icons. The selectable processes maybe located in a predefined portion of the screen different than theselectable option icons and the selectable components. In someembodiments, the selectable components may be arranged in a layoutdiagram and may correspond to one or more physical components of an oilrig (e.g., a riser connector, lower marine riser package, blowoutpreventer stack, blowout preventer, ram, annular, accumulator, testvalve, failsafe valve, kill and/or choke line and/or valve, and/or thelike). The selectable processes may comprise one or more processes formanipulating physical components of an oil rig and/or performing actionsusing physical components of the oil rig. The selectable components maycomprise selectable icons having symbols defined to represent aparticular physical component of the oil rig. In the embodiment shown,the system may continue method 100 at step 150 by receiving a userselection of a selectable component and/or selectable process. The usermay make a selection by selecting an icon from the GUI representing acomponent or a process.

In the embodiment shown, the system at step 160 may enable the displayof one or more selectable action options. In some embodiments, actionoptions for a component selection may comprise one or more options forchanging a physical configuration of the selected component, activatingor deactivating the selected component, and changing various settings ofthe selected component. Action options for a process selection maycomprise one or more steps for performing the selected process. In someembodiments, the action options may be displayed in a predefined portionof the screen different than the selectable option icons, the selectablecomponents, and the selectable processes. The action options may bedisplayed in such a way as to not obscure other elements displayed inthe GUI. In the embodiment shown, the system may continue method 100 atstep 170 by receiving a user selection of one or more action options.

In the embodiment shown, the system at step 180 may enable theperformance of a particular action or process corresponding to theaction option selected by the user and received by the system. In someembodiments, the system controls physical elements of the oil rig andmay perform the selected action on appropriate oil rig elements. In theembodiment shown, the system may repeat steps 130-180 as many times asnecessary in order to perform all actions the user desires to performduring the HMI session.

FIGS. 2-15 show examples of a GUI that may be displayed on a computingdevice. The GUI may be used by a user to implement one or more softwareapplications to perform one or more embodiments of method 100 (see FIG.1). The GUI may be implemented using a suitable operating platform, suchas Windows, Android, Apple iOS, or an internal proprietary operatingsystem.

FIG. 2 shows an embodiment of an exemplary user interface architecture200 having one or more well-defined zones or screen portions fordisplaying different types of information and controls within the HMI.One or more main “overview” screens may be accessible by the user at alltimes. This may avoid poor navigation patterns exhibited by certainprior art systems and may improve the efficiency of the user's HMIsession. In the embodiment shown, the interface architecture comprises anavigation zone 202, a system header zone 204, and a canvas zone 206.Navigation zone 202 may comprise one or more selectable iconscorresponding to various user options. These user options may correspondto the selectable options described in step 120. System header zone 204may provide the user with a high-level status of the system, a status ofalarms, a title of the current screen, and date & time information.Canvas zone 206 may provide the user with system information andcontrols. Canvas zone 206 may comprise the one or more selectablecomponents and/or processes described in step 140. In some embodiments,certain sub-portions of canvas zone 206 may be assigned to displaycertain components and/or processes.

FIG. 3A shows an embodiment of an exemplary GUI display 300 exhibitingthe three zones of the screen architecture shown in FIG. 2 as applied toa blow-out preventer (BOP) Stack option. In the embodiment shown,navigation zone 202 comprises system navigation icons 302 that mayalways be present to enable users to quickly change from one section ofthe system to another. In some embodiments, system navigation icons 302may correspond to the selectable options described in step 120. When auser selects one of user navigation icons 302, the icon may behighlighted to inform the user of the display being actively viewed. Inthe embodiment shown, the bottom left corner of navigation zone 202comprises button 304 that may begin an Emergency Disconnect Sequence(EDS). This sequence may be an option that disconnects certain physicalelements of the oil rig in the event of certain emergencies. EDS button304 may be located away from the most used controls of the system, butin a consistent, always-present location for quick access under duress.

In the embodiment shown, screen title 306 may be displayed in systemheader zone 204 to help identify what screen the user is viewing. It mayalso display a breadcrumb trail to assist the user in determining hiscurrent system level. In the embodiment shown, system header zone 204may contain a system status section 308 that may include an indicationof whether the wellbore of the oil rig is open or closed, whether thesystem is fully functional, whether failsafes are open or closed, andwhether there are any active alarms. System status section 308 mayalways be displayed in system header zone 204 so that any user can getthe high-level status of the BOP control system at a glance. In someembodiments, color, pattern, and large text can help users easily makean assessment of the BOP status, which may be important to maintainsafety during operation of the oil rig. In some embodiments, systemheader zone 204 may comprise an alarm status section 310 thatconsistently display any uncleared alarms so that the user can assess ifthere are events that need to be addressed. A time and date section 312may be displayed consistently in system header zone 204.

In the embodiment shown, a left sidebar of canvas zone 206 is whereprocedure controls and access controls may be located. In the embodimentshown, process control icon 314 may correspond to a selectable processdescribed in step 140. In some embodiments, the left sidebar of canvaszone 206 may also display processing capacity information 316 anddestructive function control icons 318. Capacity information 316 mayinform the user of the current processing capacity of the oil rig.Destructive function control icons 318 may comprise safety features thatkeep certain destructive function control modes in a default “off”status to prevent a user from accidentally performing a destructivefunction. Destructive functions may be functions that cut pipe,disconnect parts of the BOP stack, or could otherwise cause major delaysin the functioning of the oil rig if functioned accidentally. In orderto perform a destructive function, the user must consciously activatethe destructive function by selecting one of destructive functioncontrol icons 318 before performing the destructive function. A main,central zone of canvas zone 206 is where information—values,configurations, status, physical components, etc.—may be displayed. Inthe embodiment shown, a layout of one or more component icons 320 mayenable the user to view current rig operating status. In the embodimentshown, component icon 320 may correspond to a selectable componentdescribed in step 140. Various colors, symbols, and metadata may be usedto inform the user of the current state of various rig components. Aright sidebar of canvas zone 206 may comprise controls for thefunctioning of the system and/or visual status displays 322 for certaincomponents. In the embodiment shown, visual status displays may informthe user of current pressure and temperature of certain components. Upona user selection of process control icon 314 or component icon 320,details about the selected process or component are displayed in theright sidebar of canvas zone 206. In some embodiments, the only place inthe HMI where the user can cause an actual function of a component orprocess is in this right sidebar. By displaying different types offunctions in preassigned areas of canvas zone 206, the mental strain onthe user may be decreased. Further, by requiring that destructivefunctions be activated in one zone before being selectable in anotherzone, accidental activation of destructive functions may be drasticallyreduced and/or eliminated.

In some embodiments, the HMI for the BOP control system revolves aroundthe BOP Stack screen, which may be accessed upon a user selection of thecorresponding system navigation icon 302. This may be considered thehome screen for user, where they may start and end many key operationtasks. To enable the majority of important BOP tasks to be completedfrom this screen, the HMI may comprise a number of key interactionprinciples. In some embodiments, the design may utilize a color palettethat may easily inform a user of current operating conditions and mayallow for improved situational awareness. In some embodiments,functioning a component in a consistent, predictable way may be key topreventing errors (thereby reducing related downtime) and maximizinguser efficiency. In some embodiments, important structural oil rigelements such as shears and connectors are disabled by default. The usermust take a deliberate step of activating destructive functions forthese components which may prevent accidental operation. Certain presetprocedures (e.g., automatically closing the diverter, or lining up theBOP for drilling) may reduce repetitive tasks for users without removinguser control and oversight. In some embodiments, certain functions thatmay require a two-handed operation by regulation for safetyconsiderations. In some embodiments, the safety features provided by atraditional two-handed operation may be realized in other, moreefficient ways.

As discussed above, the design of some embodiments may utilize a colorpalette that allows for improved situational awareness. In someembodiments, elements colored green may indicate normal component statesrepresenting normal and error-free functioning or drilling conditions,and elements colored red may indicate abnormal component statesrepresenting problems, alarms, and errors. By only having colorrepresent these two basic states, this design may reduce the cognitiveload or amount of mental effort that users expend as they utilize thesystem. When cognitive load is low, performance time and errors maydecrease while the probability of successfully accomplishing a goal maybe increased. In this way, users may be able to easily interpretessential elements in the interface to quickly understand and respond toany situation. For example, system status section 308 may be coloredgreen when the wellbore is open and ready to function but may be coloredred when the wellbore is closed. Similarly, component 320 may be coloredgreen when that component is functioning normally but colored red whenthat component is functioning abnormally or in an alarm state. In someembodiments, green and red may not be displayed simultaneously. If thesystem is functioning in a normal state, all elements will be coloredgreen. If any element of the system is functioning abnormally, themalfunctioning component and system status section 308 may be coloredred.

FIG. 3B shows an embodiment of an exemplary GUI display 300 when acomponent icon 320 is selected. Upon a user selection of a componenticon, control options field 324 for that component may be displayed inthe right sidebar of canvas zone 206. In the embodiment shown, thecontrol options within control options field 324 may correspond toaction options described in step 160. In some embodiments, a selectedcomponent icon 320 may be outlined in a particular color to inform theuser that a component is selected. In some embodiments, the border of aselected component may be blue, and the label may comprise bold bluetext. In some prior art systems, there is a common problem where thestate of a component may be represented by a button. However, thisbutton may also be the control to change that component's state, whichcan lead to user confusion. In some embodiments, labels and actions maybe treated visually differently and the state of a component is notdepicted by the button that is also meant to change its state. When theuser selects a component 320, control options field 324 may open on theright sidebar of canvas zone 206. A blue stripe pattern may be displayedto draw a direct connection between the selected component 320 and itscontrol options field 324 on the right. Pressure/temperature visualstatus displays 322 may be repositioned within canvas zone 206 when acontrol options field 324 is opened. A state for a selected component320 may be clearly labeled in a component state field 326, which may bein close proximity to the available component functions in componentoptions field 324. The available functions may be presented in a commonorder and layout. For example, action state options 328 (e.g., Close,Pause, and Open) may always be listed left to right, regardless of thecomponent, current state, or default state. Available action stateoptions 328 may have a certain color and may be selectable whileunavailable action options may be have a different color and/or apattern. In some embodiments, unavailable action options may be a graycolor and/or may have a diagonal line pattern. In some embodiments,control options field 324 may contain one or more action status fields330 and component action options 332. Action status fields 330 mayinform the user of the progress of certain actions while componentaction options 332 may enable the user to perform various functions ofthe selected component 320. Action status fields 330 may containcontextual data (e.g., progress, gallons, time, pressure) relevant tothe selected component 320. In some embodiments, when a particularfunction is selected by the user, an icon in the action status field 330may animate to indicate the current action and show current progress ofthe function. The contextual data may also update in real-time. When thefunction is complete, the component state field 326 may update toreflect a modified state and progress bars in action status fields 330may display the modified contextual data.

Before functioning destructive components like shears and connectors,the user may need to activate the access control for that type ofcomponent by selecting one or more of destructive function control icons318. For a destructive component like a shear or a connector—i.e., anycomponent that has an initial access control—there may also be atwo-part confirmation displayed in control options field 324 beforeenabling the destructive function. In some embodiments, the two-partconfirmation comprises the selection of a checkbox and a selection of afunction activation button.

The use of destructive function control icons 318 may be a safety anderror-prevention measure. Destructive function components, such asshears and connectors, may be disabled in a default state. Activatingthese destructive components may add a deliberate step that makesaccidental operation less likely. In some embodiments, certaincomponents may not be available to be activated during certain systemmodes. For example, when the HMI system is in a drilling mode, awellhead connector component may be unable to be accessed. When the HMIsystem is in Run/Pull Mode, a riser connector component may be unable tobe accessed. In some embodiments, when the user activates one or more ofdestructive function control icons 318, the icons may be colored red tosignal to the user that the activation of these destructive componentsmay need special attention.

FIGS. 4A-4B show an embodiment of an exemplary GUI display 400 when aprocess control icon 314 is selected. Procedures (like automaticallyclosing the diverter, or lining up the BOP for drilling) are meant toreduce repetitive tasks for users without taking control and oversightaway. Depending on the procedure, the procedures require varying levelsof user interaction. In some embodiments, process control options field402 may be displayed in the right sidebar of canvas zone 206 when a userselects a process control icon 314. For some processes, a checklist forpre-function optional confirmation items may be displayed in processcontrol options field 402. These may comprise helpful reminders fortasks outside of the BOP system's control. A checklist for requiredpre-function confirmation items may also be displayed. In theseinstances, the user must select a checkbox as a precaution beforestarting the sequence or procedure. In instances where there may bemultiple ways to run the procedure, this option may be presented for theuser to select. In some embodiments, a preselected option may beconfigurable in user settings. By providing checklists for required andrecommended confirmation items and introducing a checkbox precautionstep, the disclosed embodiments may reduce operator error and increasesafety and operator confidence.

As shown in FIG. 4B, component function steps 404 may be listed withinprocess control options field 402 in the order in which they may befunctioned. This order may be predetermined by configurable proceduresettings. The user may activate the procedure by selecting processactivation button 406. As the steps in the list are completed, one ormore live progress indicators 408 corresponding to each step may displaycurrent progress of the procedure. In some embodiments, progressindicators 408 may be expandable to display additional details about aparticular step (e.g., gallon count or pressure.). After all steps ofthe procedure are complete, the user may exit the procedure by selectingprocess end button 410.

Referring back to the embodiment shown in FIG. 3A, a BOP Stack screenmay comprise a graphical representation or layout of a lower marineriser package (LMRP) and a BOP. It may include components 320 such asrams, annulars, choke and kill valves, connectors, pressure indicators,and a total gallon count. When operating the BOP, the system may presentoptions for manual control, as well as common operational procedures 314that can be pre-programmed and guide the user through the proper steps.Additionally, this screen may comprise access control modes fordestructive components 318 such as shears and connectors—components thatif functioned errantly would lead to BOP downtime. Available pressureand temperature sensor values 322 may be displayed in the canvas zone206 if there is no control panel present.

In some embodiments, when the system is in a drilling mode, only certaindestructive functions 318 such as, for example, Shear Control and LMRPConnector Control can be operable—Wellhead Connector Control may bedisabled in this mode. Conversely, when the system is in a run/pullmode, LMRP Connector Control may not be operable. The user may selectcapacity information 316 to open controls for resetting a count andviewing a detailed log of fluid usage. In the embodiment shown,components 320 that are on the wellbore and affect the ability to drillare displayed in a green color. This may provide an easy, at a glance(or across the room) view of whether or not the wellbore is open. Incertain modes, some components 320 may be disabled. Disabled componentsmay show their state through color and icon just like enabledcomponents. Both enabled and disabled components may have metadata orlabels that identify the components. These labels may be visible bothwhen the components are enabled and disabled. In some embodiments,failsafe components and valve components may be colored gray instead ofgreen unless they are in an abnormal or unexpected position. In theseabnormal cases, the component icon would be colored red.

Referring back to the embodiment shown in FIG. 3B, action status fields330 may be based on one or more algorithms that takes time, volume, andpressure into account. Knowing these three expected values, the systemmay estimate progress—and use those three values to indicate when acomponent does not function as expected. Expected values may be definedat a configuration stage, and action status fields 330 may show currentand expected values. The right-hand end of the progress bar mayrepresent the limit of whether or not the value may trigger an alarm. Inthe case of a leak, certain action status fields 330 may move all theway to the right of the progress bar, and the value's text readout maycontinue to count. The appropriate alarm may also be displayed incontrol options field 324 (along with other alarm display points) whenvalues move outside acceptable ranges.

To provide feedback when disabled components or controls are selected,the HMI may use a standard visual pattern. This pattern is designed togive feedback to verify that the system received an input from the userand indicate how a user may enable a component. For example, if a userselects a disabled component, the component icon may blink a transparentwhite color and receive a border. At the same time as the component isselected, controls related to the selected disabled component may alsoblink with the same visual indicators discussed above. After the initialblink, the white fill and gray border may fade out over a one secondinterval. The control indicator may fade out at the same rate as thecomponent indicator until the component returns to its previousappearance.

In some embodiments, the HMI may predict the presence of fluid and/orpressure in the wellbore by using a highlighted flowpath 333. In someembodiments, flowpaths where the user can expect fluid to be flowing maybe highlighted in a blue color. In the event where pressure may possiblybuild up in the wellbore, that section of the wellbore may behighlighted with an alternate color such as magenta. The main flow offluid may be highlighted blue to show where the fluid has a highprobability of flowing. Anywhere that fluid can also be flowing in thekill or choke lines may be highlighted with a blue color. Thesehighlighted flowpaths 333 may enable the user to quickly see where fluidwill likely flow and where fluid pressure may likely build up.

In some embodiments, a “normal” state of the BOP may be defined when itis initially configured. If components 320 are not in their predefinednormal states, a Line-Up procedure can be used to automatically put theminto the right state. This Line-Up procedure may comprise one of processcontrol icons 314. The Line-Up procedure may combine an awareness of thesystem's state, decide what components to function, and manuallyfunction multiple components into one automated procedure. Referringback to the embodiments shown in FIG. 4A, upon beginning a procedure,information for the selected procedure may be displayed in the processcontrol options field 402. Components 320 may not be selectable while aprocedure is running, which may be defined by any time that processcontrol options field 402 is present. The components to be functionedare determined dynamically based on current state and desired state.Pressing process activation button 406 may start performing the steps404 of the procedure. As component functions are completed, theirprogress indicators 408 show 100%, and the current function's status maybe expanded to display the progress indicator. Upon completion, pressingprocess end button 410 may close the process control options field 402and re-enable individual component 320. At any point during or after theprocedure, the individual step progress indicators 408 may be expandedto show more detailed information (e.g., time, gallon count, andregulator pressure).

In some embodiments, a sequence of actions to shut in the well may alsobe designed as a procedure in the HMI. As a procedure, it ensures that apolicy can be implemented uniformly among different oil rigs andfollowed properly by users. This Shut-In Well procedure may comprise oneof process control icons 314. The Shut-In Well procedure may have ahandful of optional items to help the user remember his training in atime of distress. Optional items are items that will not slow down thetime-sensitive act of shutting the well. An important step that may beinitially included in the Shut-In Well procedure may be the closing ofone of the annulars. This can be configured at deployment. Pressingprocess activation button 406 may immediately start functioning theselected annular. As the annular closes, progress may displayed byprogress indicators 408 and more detailed information can be found byexpanding the progress module. This detailed information may enable theuser to verify the time, pressure, and gallon count. After the annularhas closed, the user may have two options: 1) the user may view optionalsteps, which can be configured to include other components such asopening the choke valves to begin to manage the kick, and 2) exit theprocedure in order to deal with other concerns or systems. For eachoptional step, there may be additional prompts for the user to select acertain function rather than automatically firing multiple functions. Ifthe user decides to view the optional steps, the procedure may be exitedafter all optional steps are executed or considered.

In some embodiments, the control system may automatically monitor allfluid used in functioning BOP components. There may be automatic countsfor each function that may be displayed in the component options field324 for each component, but there may also be a total gallon count thatmay show the overall gallon count for all components. This total galloncount may be shown in capacity information 316. The BOP Stack screen maydisplay this overall gallon count and may also allow the user to resetit to zero. This may be useful to users when monitoring flow for purposeof both complying with regulations and verifying proper componentfunctionality. The gallon counter may visually be treated like acomponent, as an affordance that it will open up its own componentoptions field 324 on the right hand side of the screen. The only controlavailable for the gallon count may be a Reset Gallon Count button. Asmall trend line may be shown for a default past period of time with theoption to view past values in more detail.

In some embodiments, the HMI may provide audible feedback to a user upona user selection of one or more functions. For example, the BOP Stackscreen may enable the user to actuate various functions on the BOP.These functions may control components such as upper pipe rams, lowerpipe rams, annulars, and the like. Upon a user selection of a particularfunction, the audible feedback system may provide an audibleconfirmation of the selected function to the user. For example, if auser selects the upper pipe rams, an audible confirmation may be issuedto the user confirming that the upper pipe rams are selected. In someinstances, a user may be careless in the selection and may select anundesired function. In these cases, the audible confirmation may alertthe user to the incorrect selection and allow the user to make thecorrect selection before the function is initiated. In the exampleabove, the user may have mistakenly selected the upper pipe rams insteadof the lower pipe rams. When the user receives the audible confirmation,the user may realize that he selected an undesired function. The usermay then go back and select the lower pipe rams and receive an audibleconfirmation before any functions are initiated. Therefore, the audiblefeedback system may provide another safety element that may alert a userto possible carelessness and mitigate damage that may otherwise becaused to the BOP due to accidental function initiation.

FIG. 5 shows an embodiment of an exemplary GUI display 500 when a userselects a Surface Systems option. In the embodiment shown, state optionfield 502 may comprise one or more surface system component option icons504 that may give the user access to the current state of varioussurface system components. These surface system components may include aFluid Mixing Unit, a Hydraulic Power Unit, a Hotline & Conduit ValvePackage (HLCVP), and a band of Surface Accumulators. Graphicrepresentations of those systems may be used when appropriate. Uponselection of a surface system component option icon 504, the componentstatus information may be displayed in a central portion of canvas zone206. In some embodiments, a representative depiction 506 of the selectedsystem may be displayed, including components and sensors that can bemonitored and controlled.

In some embodiments, the Hydraulic Power Unit, in conjunction with theSurface Accumulator Bank, may be responsible for supplying pressurizedhydraulic flow to on-stack common rails through rigid conduits andhotlines. The Fluid Mixing Unit may store additive concentrate andglycol and deliver metered additive concentrate, glycol, and potablewater to a Hydraulic Power Unit reservoir tank. The Surface AccumulatorBank may be responsible for stored hydraulic energy for nominaloperations of the BOP. The Hotline and Conduit Valve Package (HLCVP) maybe responsible for providing fluid filtration subsea, diagnosing fluidquality, providing a means to isolate and flush rigid conduits andhotlines, and connecting surface pressure sources to common rails.

FIG. 6 shows an embodiment of an exemplary GUI display 600 when a userselects an Electronic Riser Angle option. These screens may displayinformation about the position and angle of the BOP and riser. Thisinformation may be visualized on an X-Y graph as well as a tabularformat. In the embodiment shown, a vertical overview 602 of the riserangle may be displayed on a left side of canvas zone 206. A top-downvisual summary graph 604 of the riser angle information may be displayedon a right side of canvas zone 206. In the embodiment shown, a user canselect one or more of a plurality of viewing option icons 606 to viewthe angle information in top-down visual summary graph 604.

FIG. 7 shows an embodiment of an exemplary GUI display 700 when a userselects a Diverter option. This option may show the state of severalvalves, regulators, and other devices related to a diverter and may alsofacilitate changing pressures. This option may need to be configurableas each rig may have a different diverter setup and components. In theembodiment shown, process option field 702 may comprise one or moreprocess option icons 704 that may give the user quick access to one ormore automated and guided procedures such as a Diverter Close sequenceand a Line Up for Drilling sequence. In some embodiments, arepresentative depiction 706 of the diverter system may be displayed togive the user an overview of the state of the riser and the state of keyconnection components. The components may be organized by how they arephysically connected. One or more dog components may be shown separatelyfrom the diverter system depiction in the left side of canvas zone 206.In some embodiments, pressure/temperature visual status displays 708 maybe available to enable the user to monitor pressure and temperaturereadings for various components.

Similar to the embodiments discussed above, the user may select acomponent from representative depiction 706 to open a component controlfield (not shown but similar to component options field 324) on theright side of canvas zone 206. The component control field may compriseelements similar to component state field 326, available action stateoptions 328, one or more action status fields 330, and component actionoptions 332, as shown in FIG. 3B. The user may initiate an operation byselecting one or more action state options 328. The various componentsrepresentative depiction 706 may have differing states for display incomponent state field 326. For example, valves may have open and closedstates, packers may have energized and de-energized states, and dogs mayhave latched and unlatched states. Action status fields 330 may compriseprogress indicators that may show current and expected values.Associated regulator elements may also be controlled from the componentcontrol field.

In the embodiment shown, diverter procedures and sequences correspondingto process option icons 704 may be programmed, presented, and operatedsimilar to the embodiments shown in FIGS. 3A-B. A Diverter Auto CloseSequence or a Line Up for Drilling Sequence may be activated by the userselecting the corresponding process option icon 704. In these instances,the control system may evaluate the state of each affected component andproduce a sequence of control events (e.g., open, close, latch,energize) that hydraulically optimizes the efficiency of the systemreaching the new state. For the Diverter Auto Close Sequence procedure,the components may go to these states when the sequence is initiated:Diverter Locking Dogs EXTEND, Flow Line Seals ENERGIZE, Master OverboardVent Valve OPEN, Port (or Starboard) Vent Overboard Valve OPEN, FlowLine Valve CLOSE, Trip Tank Return Valve CLOSE, Lower Solid PackerENERGIZE, Diverter Packer CLOSE. For the Line Up Diverter for Drillingprocedure, the components may go to these states when the sequence isinitiated: Flow Line Valve OPEN/CLOSED depending on whether the drillerlines up on the Flow Line or Trip Tank Return Line, Fill Up ValveCLOSED, Test Line Valve CLOSED, Trip Tank Return Valve OPEN/CLOSEDdepending on whether the driller lines up on the Flow Line or Trip TankReturn Line, Water Injection Valve CLOSED, Diverter Packer OPEN,Diverter Locking Dogs EXTENDED, Insert Packer Locking Dogs EXTENDED,Master Overboard Valve CLOSED, Mud Gas Separator Valve CLOSED, TensionRing to Diverter Housing Dogs EXTENDED, Telescopic Joint Latch DogsEXTENDED. The user may activate the selected sequence to initiate thesteps in the procedure to occur automatically. While the sequence isbeing performed, the user may have the ability to see additional detailsfor gallon count, pressure, and elapsed time for each step of theprocedure.

FIG. 8A shows an embodiment of an exemplary GUI display 800 when a userselects a Diagnostics option. In the embodiment shown, the Diagnosticsscreen may present information about alarms, events, and otherindicators that may impact the readiness of the BOP. The Diagnosticsscreen may also present an overview of the BOP's readiness and state ofcompliance with regulatory standards. In the embodiment shown, aregulatory status panel 802 may list one or more primary complianceregulations 804 that must be verified in order to safely secure thewell. In the embodiment shown, if any of the regulations 804 listedbecome untrue or unavailable, then the system may be considered out ofcompliance with regulatory standards. In some embodiments, the well maybe shut down until diagnosis and correction of the non-compliantfunction or component may be performed. In the embodiment shown, a usermay select a primary compliance regulation 804 to navigate to a BOPfunction detail screen for a function that is causing the system to beout of compliance. In some embodiments, if the system is out ofcompliance, clicking anywhere within regulatory status panel 802 mayautomatically take the user to the first function that is causing thesystem to be out of compliance. In some embodiments, if the system isnot out of compliance, clicking anywhere within regulatory status panel802 may automatically take the user to the first function listed in thepanel. In the embodiment shown, an events overview panel 806 may displaya chronological view of the most recent events both initiated by andreceived by the control system. In some embodiments, clicking anywherewithin the events overview panel 806 may take the user to one or moreevent log screens. In the embodiment shown, an operational status field808 may provide a summary of the operational readiness of varioussubsystems 810 of the control system. In some embodiments, clicking onone of the individual subsystems 810 in this field may enable a user tonavigate to a diagnostic summary screen for the selected subsystem.

FIG. 8B shows an embodiment of an exemplary GUI display 800 when a userselects a BOP Components option within the Diagnostics option. Thedisplay 800 shown in FIG. 8B may be displayed upon a user selection of asubsystem 810 from operational status field 808 shown in FIG. 8A. In theembodiment shown, one or more display category option icons 812 may beselected. In some embodiments, a BOP Component Information screen may bedisplayed as a default screen or upon a user selection of thecorresponding category option icon 812. Selecting a component 814 fromthe BOP Component Information screen may bring up detailed diagnosticinformation about the selected component in component options field 816.However, in the embodiment shown, the options contained in componentoptions field 816 are disabled and component 814 cannot be functionedfrom this screen. The Diagnostics option may fulfill several key systemrequirements. For example, the system may keep a count and be able todisplay the number of times a device is operated (e.g., opened orclosed). The system may also track maintenance data on each part of theBOP. Information tracked might include but might not be limited toinstall date, part number, last checked date, and number of operations.The system may also indicate when components are reaching mean failuretimes or when the number of operations approaches or exceeds recommendednumbers. In addition, the Diagnostics option may be accessible based onuser role. For example, some users may have greater diagnostic accessprivileges than other users.

FIG. 8C shows an embodiment of an exemplary GUI display 800 when a userselects a BOP Functions option within the Diagnostics option. In someembodiments, the BOP Function Details screens will show the operatingpath to specific BOP components. In the embodiment shown, one or morecomponent option icons 808 may be selected. Upon selection of acomponent option icon 818 by the user, one or more component functionfields 820 may be displayed in canvas zone 206 corresponding tofunctions available for the selected component. Component functionfields 820 may comprise one or more diagnostic displays. For example, achannel control may allow the user to view diagnostic information for anactive channel or allow the user to manually view any of the channels. Aregulator pressure may be displayed as both the instantaneous value andthe running trend. An Integrated Manifold may be represented as afunctional valve block. In some embodiments, the state of the valves maybe displayed as an overall state of either Standby, Actuating, orVenting. A flow volume and/or rate may be displayed as a graphicaltrend. Component control field 822 may comprise controls for activatingthe component function for the selected component function field 820.The user may select various options within component control field 822to activate various aspects of the selected component function. Forexample, the user may choose a particular hydraulic source system tooperate the function or choose a particular channel of the integratedmanifold to operate.

FIG. 8D shows an embodiment of an exemplary GUI display 800 displayingdetailed compliance data. The display 800 shown in FIG. 8D may bedisplayed upon a user selection of a primary compliance regulation 804from regulatory status panel 802 shown in FIG. 8A. In the embodimentshown, various operating paths to specific BOP components may beillustrated. In the embodiment shown, a function navigation panel 824may display a list of selectable BOP functions to allow a user to easilynavigate to a desired function. Upon a user selection of a BOP functionfrom function navigation panel 824, a diagnostics decision path tree 826may be displayed. Decision path tree 826 may represent the regulatorycompliance states of all rig components involved in performing theselected BOP function. Diagnostics decision path tree 826 may compriselevels 828, nodes 830, and pathways 832 that can connect certain nodestogether. Each level 828 may correspond to a particular rig componentand each node 830 may correspond to a particular function performed bythat component. In the embodiment shown, levels 828 correspond tocomponents such as an integrated manifold assembly, a regulator, acommon rail, and a rigid conduit and hot lines that are involved withperforming the Close Upper Annular function selected by the user infunction navigation panel 824. At each of the nodes 830, an icon 834 maybe displayed that may inform the user whether a particular function orcomponent is operating properly and compliant with regulations.

Diagnostic details 836 may be displayed to assist the user in performingdiagnostic functions. For example, in the embodiment shown, diagnosticsdecision path tree 824 may display all of the available hydraulicpathways through the rig components listed in levels 828 for theselected function. In the embodiment shown, each function may have threepossible channels, each represented by a pathway 832 in decision pathtree 826. Diagnostic details 836 may be displayed that may representdetailed measurements for each of these channels when a function isoperated. In the embodiment shown, diagnostic details 836 may includeregulator pressure, common rail pressure, function pressure, and ventpressure. The regulator pressure may be displayed as both aninstantaneous value and a running trend. In the embodiment shown, afunction control field 838 may be specific to the function selected inthe function navigation panel 824. While function control field 838 mayinclude multiple functions, only a selected function may be executed. Insome embodiments, in function control field 838, the user may be able tochoose which hydraulic source system may operate a function, or whichchannel of the integrated manifold may be activated. By accessingelements in diagnostic details 836 and function control field 838, theuser may be able to access rig components or functionalities that maynot be in compliance and perform corrective action. As the user performscorrective action, icons 834 may change to inform the user that afunction or component that was previously non-compliant is now currentlycompliant.

When a user selects a level 828, the currently selected level may bedisplayed with a selection border of a particular color such as blue. Asimilar selection border may also denote currently selected functionsfrom navigation panel 824 or other currently selected icons in the GUIdisplay 800. In some embodiments, display 800 may change to correspondto the currently selected level. More specifically, upon a selection ofa particular level 828, diagnostic details 836 may change to correspondto the selected level. For example, if a level 828 corresponding to anintegrated manifold assembly is selected, display 800 may change todisplay diagnostic details 836 and function control field 838 associatedwith the integrated manifold assembly. The display may similarly changeto correspond to the selection when a regulator, a common rail, or rigidconduit and hot lines is selected.

In some embodiments, upon a user selection of the corresponding level828, an integrated manifold display may give a single view of the stateof hydraulic pressures within an integrated manifold. Pressure readingsmay be read on both the input and output sides. Diagnostic details 836may include integrated manifold summary information, electrical controlstatuses, and input and output pressures for each of three flowchannels. Function control field 838 may change to display functionsassociated with the integrated manifold assembly that may be selected bythe user to perform various diagnostic and/or corrective functions.

In some embodiments, upon a user selection of the corresponding level828, a regulator display may give a single view of the state ofhydraulic pressures within a regulator group. Pressure readings may beread on both the input and output sides of each regulator. The statusand pressure readings from each regulator in a regulator group may beincluded in a summary of each regulator assembly. Diagnostic details 836may include the regulator assembly summary information, electricalcontrol statuses, and input and output pressures for each of three flowchannels. Diagnostic details 836 may also display data and correspondingfunctions associated with each integrated manifold connected in achannel downstream from the regulator. The user may select one or morefunctions from diagnostic details 836 to navigate to the selectedintegrated manifold function. Function control field 838 may change todisplay functions associated with the regulator assembly that may beselected by the user to perform various diagnostic and/or correctivefunctions.

In some embodiments, upon a user selection of the corresponding level828, a rigid conduit and hot lines display may give a single view of thestate of hydraulic pressures within a hot line and rigid conduit valvepackage. Pressure readings may be read on both the input and outputsides of each valve package. The status and pressure readings from eachrigid conduit and hot line may be included in a summary of each valvepackage. Diagnostic details 836 may include the rigid conduit and hotline summary information, electrical control statuses, and input andoutput pressures for each of three flow channels. Diagnostic details 836may also display data and corresponding functions associated with eachrigid conduit and hot line valve package. The user may select one ormore functions from diagnostic details 836 to navigate to the selectedrigid conduit and hot line function. Function control field 838 maychange to display functions associated with the valve package that maybe selected by the user to perform various diagnostic and/or correctivefunctions.

In some embodiments, upon a user selection of the corresponding level828, a common rails display may give a single view of the state ofhydraulic pressures within a subsea system. Flow meters and pressurereadings available from a downstream portion of a hot line and rigidconduit valve package may be displayed in diagnostic details 836.Diagnostic details 836 may also display data for each of the downstreamregulator assemblies. The status and pressure readings from eachregulator may be included in a summary of each regulator assembly.Diagnostic details 836 may also include common rail summary informationand electrical control statuses. Diagnostic details 836 may also displaydata and corresponding functions associated with each regulatorconnected in a channel to the common rail. The user may select aparticular regulator from diagnostic details 836 to navigate tofunctions corresponding to the selected regulator. In some embodiments,the system may navigate to a first default function for the selectedregulator. As the user selects different regulators for diagnosis,decision path tree 826 may be modified to show a level 828 correspondingto the selected regulator as currently selected. Function control field838 may change to display functions associated with the regulator thatmay be selected by the user to perform various diagnostic and/orcorrective functions.

FIG. 9 shows an embodiment of an exemplary GUI display 900 of adiagnostic event log. In the embodiment shown, the event log may providethe user with information about the operation and performance of theentire BOP control system. In the embodiment shown, a series of filtersfor the events may be listed in a filter options field 902. Thesefilters may include date ranges, affected systems, or event types. Inthe embodiment shown, a timeline field 904 of events may be displayedbased on the filter options selected in filter options field 902.Sliding controls 906 may provide additional filtering functionality.Sliding controls 906 may be moved horizontally along the timeline toselect a time interval for displayed events. The events within theselected time interval may be displayed in an event list field 908 in atabular format and may display event details and attributes. A user mayselect an event from the timeline field 904 or event list field todisplay additional details about the selected event in detail field 910.The full event details may be presented in detail field 910 along withpossible links to related events or affected systems. The user mayselect a filter icon 912 to quickly view other events of the same typeas the selected event. Each event may comprise a number of attributesand values in order to provide value to the user through the interface.This will also enable the filtering and visualization features depictedin the Events Log screen.

FIG. 10 shows an embodiment of an exemplary GUI display 1000 of apressure/temperature log. In the embodiment shown, apressure/temperature log may display the historical data of a selectedpressure and temperature sensor. In some embodiments, thepressure/temperature log may be accessed by a user selection of any ofthe pressure and temperature sensor readings of the visual statusdisplays 322 shown in FIG. 3A. In the embodiment shown, a series offilters for the events may be listed in a filter options field 1002.While a selection of the pressure and temperature sensor from aparticular visual status display 322 may have already applied certainfilters, these filters may include time ranges and other filter types.In the embodiment shown, a visualization field 1004 may displaytemperature and pressure graphed over a time period selected from filteroptions field 1002. Detailed data points from the visualization field1004 may be listed in a table 1006. Upon selection of an event fromtable 1006, additional details of the selected event and the componentor sensor may be presented in detail field 1008.

FIG. 11 shows an embodiment of an exemplary GUI display 1100 of a BOPComponent log. In the embodiment shown, a BOP component log may displaythe history of a component's functions. In the embodiment shown, aseries of filters for the events may be listed in a filter options field1102. These filters may include event number ranges and function types.In the embodiment shown, a visualization field 1104 may display datarelevant to the selected function type and graphed over an event numberrange selected from filter options field 1102. In the embodiment shown,the historial gallons and seconds of an Upper Annular's Close functionare both graphed for a specific number of past events. Detailed datapoints from the visualization field 1104 may be listed in a table 1106.Upon selection of an event from table 1106, additional details of theselected event and the component may be presented in detail field 1108.

Referring back to the embodiment shown in FIG. 8A, a Regulators categoryoption icon 802 may display a single view of the state of the hydraulicpressures within subsea components. Canvas zone 206 may be used todisplay a representative depiction of regulators and their operationstate. Each regulator may be named and metadata may include adescription of affected components, an operational range, setpoint, andreadback values. An Integrated Manifolds category option icon 802 maydisplay a summary of all of the manifolds, and may allow the user to seedetails of valve positions and pressures within the manifolds. Canvaszone 206 may be used to display a representative depiction of integratedmanifolds and their operation state. Each manifold may have severalvalves and pressure readings.

The Communications system corresponding to category option icon 802 maybe responsible for transferring commands and data between the variousHMI interfaces and the physical subsea components and may display arepresentative depiction of the communications network. Each node in thecommunication network may have the ability to monitor severalself-diagnostic attributes such as temperature and water ingress.Examples of information that may be available for diagnostics include astate of physical media links, a log of communications activity, acommunications message counter, communication nodes status, andcommunication packet corruption detection.

A Hydraulics category option icon 802 may display a list of Hydraulicpower sources to allow for easy navigation. Canvas zone 206 may be usedto display a representative depiction of pumps and motors and theiroperation state. Clicking on an item in the Hydraulic power sourcessection may update the view in canvas zone 206. A new event may begenerated for each time a motor starts. These events may be depicted toshow how many motors run and their impact on overall system performance.Current events may be displayed in more detail. Motors that arecurrently running may be depicted with trend lines while non-operatingmotors may have a high-level summary of their state displayed. AReservoir category option icon 802 may display a representativedepiction of fluid reservoirs. An Electrical system corresponding tocategory option icon 802 may be responsible for transferring electricalpower from the surface to the subsea components and may display arepresentative depiction of the electrical network. The electricalnetwork may be similar to the communications network, but may displayelectrical measurements.

FIG. 12 shows an embodiment of an exemplary GUI display 1200 when a userselects a Testing option. The Testing screens may give users automatedrecording mechanisms for periodic tests that are required by regulatorybodies, and that help with early detection of functional issues. In someembodiments, the testing system may facilitate the running of functiontests and pressure tests in both a manual way (e.g., full userinteraction) and a guided way (e.g., periodic user interaction). Thesystem may also keep a count and be able to display the number of timesa device is operated (e.g., opened or closed). Function tests may haveprogrammed expected gallon counts, and times to close/open. The systemmay also indicate when expected gallon counts or times to close/open areexceeded and may track maintenance data on each part of the BOP.Information tracked might include but might not be limited to installdate, part number, last checked date, and number of operations.

GUI display 1200 may comprise a test category field 1202 that gives theuser options to perform a new test, a test status field 1204 comprisinga table displaying operational information about individual systemcomponents, and a past function test field 1206 and a past pressure testfield 1208 for showing recently performed function and pressure tests.The test status field 1204 gives the user information about eachcomponent including the number of actuations and the last operated timeand/or date. This information may be used to determine whether or not acomponent should be tested or not. Each prior test listed in pastfunction test field 1206 and past pressure test field 1208 may include acheck mark if the tests passed or an indication of the number of issuesthat were found. Clicking on one of these items may display a TestReport to the user.

In the some embodiments, the HMI may support three types of tests:Function tests, Pressure tests, and Other tests. Function tests maytypically be run every 7-14 days and may take a couple of hours tocomplete. If the operator selects Function Test from test category field1202, test status field 1204 may be populated with components that aredue to be tested. In some instances, the user can add or removecomponents before starting the test. The user can function components inany order, which may be reflective of normal BOP functioning. A Resultspage may be viewed after the desired tests are performed. Items thatneed attention would go to the top of the list and details about eachitem may be viewed by selecting an item on the list. Pressure tests maytypically be run every 14-21 days and may take several hours tocomplete. If the operator selects Pressure Test from test category field1202, the system would follow the pattern from the Function Testdescribed above. The system may allow for unstructured “other” tests tobe recorded which may allow for a more granular analysis, as the eventlog identifies all actions during this time as part of a test. Forexample, if the user wants to perform a simple sensor-based test like aCasing Integrity test, selecting “Other” would allow the user to selectas many or as few components or sensors to be recorded as needed. Thesystem may then allow the user to run the test on his own without anyextra overhead. The big benefit to the user may be the automatedrecording of all sensors and components from the test.

Once a test has been selected from test category field 1201, the usermay enter some general information about this test and select a subsetof components to be tested. Information about that particular testinstance may be recorded by the user. Several fields can beautomatically populated based on information that is unlikely to change(e.g., Rig and Well) as well as information that the system is likely toalready know (e.g., dates). Components to be tested may be selectablefrom the list of all components. Selection may be defaulted to includeonly those components that have not been tested or operated within anallowable time period.

When the user begins a test, the user may be guided through theoperation of each selected component or may choose components at will totest. The user may choose to follow the list in order or select items asdesired. Components may be selected for testing either through anavigational list or a component diagram. The component may then beoperated as normal through the typical operator interface shown in theBOP Stack screen of FIG. 3A. This guided testing may be beneficial tothe user by drastically reducing the time the user spends testing. Itmay also reduce overall testing time of the rig components, increasingthe time the components may be available to perform their respectivefunctions.

When testing is complete, a results summary page can be reviewed toallow the user to understand errors and look for impending conditionsthat may impact operational ability. The user may select options to editand save overview attributes of the test. A Component Report table maydisplay warnings, errors, and basic status of the testing of eachcomponent. Details of that component's test may be also be displayed.Associated sensor values may also be recorded and displayed based on thecomponent that was functioned. Details of the selected component mayalso be displayed, including information about similar prior tests,allowing the user to see how the current test related to other test oroperation events.

FIG. 13 shows an embodiment of an exemplary GUI display 1300 when a userselects a System Settings option. The System Settings screens may allowfor configuration of the software to match the hardware and proceduresfor a particular rig environment. The Settings option may be used tomake choices about how the BOP system will function. This may include asystem operation mode and the pre-selected, or default, choices forauto-sequences such as the diverter auto-close sequence or the emergencydisconnect sequence. Some changes may require a user login to apply toensure that only user having necessary credentials may change the systemsettings.

The user may also configure the components of the BOP. This willtypically be done at BOP commissioning on the rig, or during majoroverhauls to the equipment. A component field 1302 may display variouscomponents that can be added to a BOP diagram 1304 displayed in canvaszone 206. The user may use BOP diagram 1304 as a blueprint to assemblethe virtual BOP stack interface. Configuration field 1306 may compriseoverall system parameters as well as detailed component parameters. Theoverall stack configuration can be entered including number of annulars,preventer, and valves. In some embodiments, the user may click and draga component symbol 1308 from component field 1302 to a location in theBOP diagram 1304. The user may add choke and kill lines to the BOPdiagram 1304 by dragging and dropping line components 1310. Eachcomponent may have specific attributes that may be used throughout theoperation of the system and in managing maintenance plans. In someembodiments, clicking on a component symbol 1308 may open an editableinterface to input attributes of the component including name,manufacturer information, and sizes.

The system may have a number of automated sequences to put the systeminto a known configuration of component states. These configurations maybe defined prior to operations, and may be re-defined at a later time.The system may provide programmable interfaces to create logic-basedconditions and reactions. For example, guided procedures for wellcontrol activities such as shut-in may be provided. Components can beadded, removed, or reordered by the user.

In some embodiments, an Alarm Rules screen may allow the user theability to view detailed information about alarm rules and an AlarmConfiguration Screen may allow the user the ability to configure anynumber of alarms. For example, the BOP control system may be augmentedwith input from gas sensors in critical drilling areas. Alarms may betriggered by these sensors and reaction procedures initiated by thesystem. Alarms may be configurable to trigger on components due formaintenance based on usage. When in an editing mode, the alarmparameters may become fields that logically map to the type ofinformation that may be entered, including radio buttons, pull-downlists, and text fields.

At times, when components or their functions fail, or during variousoperating phases or states, operators may want to lock out interfacecontrol. The operator may have the ability to define a function on aspecific channel or across all channels. When lockouts are changed, theoperator may need to apply the changes before they will take effect.Changes may also be discarded and the lockouts returned to the defaultstate. Various System Modes may create lockouts that may be defined bythe operator as modes of operation. Each mode can be defined as acollection of components and states. Components and states may be added,removed, or moved by the user.

Operating procedures shall can define how account access is set up.Login accounts may be created and shared or given to individuals. Whenconfiguring accounts, account information may be displayed in a tabularformat. Basic account information may include user name, password, firstname, last name, email address and/or other contact information,operator role or type (e.g., Subsea Engineer, Driller, Tool Pusher,etc.), and access level. The list of accounts may be editable by thosewith a certain level of account privileges. Additional information maybe stored with each user account and may include details about prioractivities and last login time/date.

FIG. 14 shows an embodiment of an exemplary GUI display 1400 when a userselects an Alarms option. An alarm may be an audible and/or visiblemeans of indicating to the user an equipment malfunction, processdeviation, or abnormal condition that requires action. The alarm mayindicate a problem that requires a response, not a normal processcondition. An Alarm Overview screen may give the user quick access tothe most urgent, active alarms, and enable the user to take correctiveaction. The user may perform corrective actions while on an alarms pageor may navigate to the BOP system page that is experiencing the alarmevent to obtain additional context on the cause. Alarm analysis icon1402 may allow the user to navigate to an Alarm Analysis page, whereusers can view and manipulate data visualizations such as “alarmresponse time by event.” The user may select an alarm selection option1404 to access alarms by category. Active alarms may be selected andshown by default, and, in some embodiments, all active alarms may beshown at all times to the user. The user may choose to show shelvedalarms or all alarms in addition to active alarms by selecting theappropriate alarm selection option 1404. In some embodiments, the usermay select global acknowledge icon 1406 to have the option toacknowledge all active alarms at once. For convenience, the alarm listcan be exported as a PDF document or printed by selecting a list outputoption 1408. In alarm list field 1410, alarms may listed in the orderthat they occur so that users can determine if there are anydependencies across the alarms. The user may select an entry in alarmlist field 1410 to populate status bar 1412 and alarm information field1414. A selected active alarm may appear as a notification in the statusbar 1412. The notification may include an alarm priority level and analarm message. The details of the selected alarm may appear in alarminformation field 1414 and include the response time remaining, alarmreaction time, a visualization of the values that tripped the alarm, andthe affected system.

In the embodiment shown, an alarm reaction time visualization may informthe user of the times the alarm was triggered, silenced, acknowledged,and/or cleared. A user may select affected system details from alarminformation field 1414 to navigate to a display providing additionaldetails and context on the alarm and functions for addressing the alarm.Alarm data may be provided in alarm information field 1414 to show theuser alarm activation points, alarm current values, and how the alarmvalues changed between the time the alarm occurred and the time thealarm was cleared. In the embodiment shown, alarm information field 1414may include fields for the user to make notes after alarms areacknowledged or shelved. In some embodiments, alarm information field1414 may list direct consequences of ignoring an active alarm andactions the user may take to correct the issue causing the alarm. Analarm overview bar 1416 may be displayed and may relate the number ofactive alarms across all priority levels. Alarm overview bar 1416 may bedisplayed persistently in system header 204 for all interface options.Any user may silence or acknowledge an alarm by selecting an alarmaction button 1418. By selecting one or more alarm option buttons 1420,any operator may flag an alarm as a nuisance so that problem alarms canbe identified during alarm maintenance. The Past Alarm button may allowthe user to navigate to an Alarm Analysis screen, which may display apre-filtered list of instances of this alarm type. Shelving an alarm, ifavailable for a particular alarm, may prompt the user to make a noteexplaining the circumstances under which he chose to shelve it.

When an alarm is triggered, an alarm message may be displayed in thestatus bar 1412 at the top of the screen, and can be seen regardless ofwhich screen is selected. Alarm notifications may also appear, whenapplicable, right on the alarming component or within its control panel.At all times, user can also see overall alarm status via alarminformation field 1414 at the top right. Alarm information field 1414may contain categories such as alarm reaction time, an analysis of thecomponent related to the alarm, and a notation of the systems affectedby the alarm. Other fields, such as notes, consequences of the alarm,and corrective actions, may be displayed. When an alarm is detected bythe system and triggered, an audible warning may sound and the alarmmessage may appears in the status bar 1412. The message has ared-colored background and may blink, but the text displaying thepriority level number and message may remain static so that they can beeasily read by the user. The blinking may continue until the operatorhas selected the Acknowledge alarm action button 1418 for that alarm.The operator can select the Silence button to turn off the audiblewarning sound. To navigate to the Alarm Overview screen, the operatorcan tap anywhere on the status bar 1412. In some embodiments, when auser is accessing the BOP stack screen, an alarm indicator may appear onalarming components and may remain until the alarm has cleared.

After the user has seen an alarm notification, the user may reviewrelated alarm information in detail in alarm information field 1414. Thealarm may remain in the alarm list field 1410 until it has both beencleared and been acknowledged by the user. To scroll through all of thealarms in alarm list field, the user can use scrolling buttons. The usermay choose to tap the Shelve button in alarm option buttons 1420 for anactive alarm in order to temporarily remove it from the alarm list field1410. After a set duration (which can be adjusted in Settings), thealarm may reappear in the alarm list field 1410 to be managed like anyother alarm.

FIG. 15 shows an embodiment of an exemplary GUI display 1500 when a userselects an Emergency Disconnect Sequence (EDS) option. The EDS button1502 may be persistent onscreen for all interface options. To initiatethe process, the operator may select the EDS button, which may causecontrol panel 1504 to appear and a transparent screen to appear over therest of the interface. This may bring more prominence to the controlpanel 1504 and strongly signal to the user that a destructive action isbeing started. The user may have the option to change the sequence typebefore firing the function by selecting one or more of sequence typebuttons 1506. The user may then select the checkbox 1508 to confirm theintention to start EDS. At this point, the Proceed button 1510 may bedisabled. When the user selects the checkbox 1508, the Proceed button1510 may be activated. After the user selects the Proceed button 1510,the sequence may commence. As the equipment associated with EDSfunctions (e.g., unlatching choke and kill lines), text that describesmay appear along with a function progress bar. Time and volume valuesmay also be displayed. As the EDS sequence proceeds, the components onthe BOP stack may show their status through color changes, blinking, andicon state changes. When the EDS sequence is complete, an Exit button(not shown) may appears at the bottom of the control panel 1504 whichthe user may select to dismiss the control panel. When this is done, thetransparent screen may be removed. The changes to the components on theBOP stack may be reflected in their current states, shown on the BOPscreen.

FIG. 16 shows an embodiment of an exemplary client-server interfaceaccording to an embodiment of the HMI system. In some embodiments, theHMI system may comprise one or more clients 1602 and one or more servers1604 that may interact with each other. In the embodiment shown, client1602 may be a hardware computing device that comprises one or moreprocessors 1606, one or more memory devices 1608, and a user interface1610. In the embodiment shown, servers 1604 may be hardware computingdevices that comprise one or more processors 1612 and one or moresoftware applications 1614. In some embodiments, the user may accessclient 1602 through user interface 1610 and enter inputs that instructclient 1602 to access one or more software applications 1614 from one ormore servers 1604 to perform one or more different functions availablein the HMI system. In the embodiment shown, client 1602 and servers 1604may be connected via one or more wired and/or wireless networks 1616(e.g., Ethernet, WAN, LAN, Wi-Fi, telephone switching network, and/orthe like).

It may be appreciated that the functions described above may beperformed by multiple types of software applications, such as webapplications or mobile device applications. If implemented in firmwareand/or software, the functions described above may be stored as one ormore instructions or code on a non-transitory computer-readable medium.Examples include non-transitory computer-readable media encoded with adata structure and non-transitory computer-readable media encoded with acomputer program. Non-transitory computer-readable media includesphysical computer storage media. A physical storage medium may be anyavailable medium that can be accessed by a computer. By way of example,and not limitation, such non-transitory computer-readable media cancomprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage,magnetic disk storage or other magnetic storage devices, or any otherphysical medium that can be used to store desired program code in theform of instructions or data structures and that can be accessed by acomputer. Disk and disc includes compact discs (CD), laser discs,optical discs, digital versatile discs (DVD), floppy disks and Blu-raydiscs. Generally, disks reproduce data magnetically, and discs reproducedata optically. Combinations of the above are also included within thescope of non-transitory computer-readable media. Moreover, the functionsdescribed above may be achieved through dedicated devices rather thansoftware, such as a hardware circuit comprising custom VLSI circuits orgate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components, all of which arenon-transitory. Additional examples include programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices or the like, all of which arenon-transitory. Still further examples include application specificintegrated circuits (ASIC) or very large scale integrated (VLSI)circuits. In fact, persons of ordinary skill in the art may utilize anynumber of suitable structures capable of executing logical operationsaccording to the described embodiments.

The above specification and examples provide a complete description ofthe structure and use of illustrative embodiments. Although certainembodiments have been described above with a certain degree ofparticularity, or with reference to one or more individual embodiments,those skilled in the art could make numerous alterations to thedisclosed embodiments without departing from the scope of thisinvention. As such, the various illustrative embodiments of thedisclosed methods, devices, and systems are not intended to be limitedto the particular forms disclosed. Rather, they include allmodifications and alternatives falling within the scope of the claims,and embodiments other than those shown may include some or all of thefeatures of the depicted embodiment. For example, components may becombined as a unitary structure and/or connections may be substituted.Further, where appropriate, aspects of any of the examples describedabove may be combined with aspects of any of the other examplesdescribed to form further examples having comparable or differentproperties and addressing the same or different problems. Similarly, itwill be understood that the benefits and advantages described above mayrelate to one embodiment or may relate to several embodiments.

The claims are not intended to include, and should not be interpreted toinclude, means-plus- or step-plus-function limitations, unless such alimitation is explicitly recited in a given claim using the phrase(s)“means for” or “step for,” respectively.

1. (canceled)
 2. A computing system for implementing a human machineinterface (HMI) application, the computing system comprising: a memorydevice; and at least one processor configured to enable the display of agraphical user interface (GUI) comprising one or more graphical elementsconfigured to implement, using the at least one processor, one or moresoftware applications stored on one or more servers, the one or moresoftware applications configured to: initiate a session of the HMIapplication by receiving a user input on a user interface running orstored on a hardware device comprising at least one processor; enablethe display of a plurality of non-overlapping zones comprising an actionzone; enable the display of a plurality of selectable action options inthe action zone, the action zone comprising a plurality ofnon-overlapping subzones, the subzones comprising two or more of: aninterface control subzone, an information subzone, or a system controlsubzone; receive, at the hardware device, data representing a userselection of one of the one or more selectable action options; andcontrol an operating state of one or more physical offshore drilling rigcomponents based on the user selection.
 3. The computing system of claim2, where the HMI application is configured to implement one or morestandard operating procedures applicable to one or more offshoredrilling rigs.
 4. The computing system of claim 3, the HMI applicationfurther configured to: receive, at the hardware device, datarepresenting one or more modifications to the one or more standardoperating procedures; apply the one or more modifications to the one ormore standard operating procedures to create one or more modifiedstandard operating procedures; and apply the one or more modifiedstandard operating procedures to the one or more offshore drilling rigs.5. The computing system of claim 2, the one or more softwareapplications being further configured to: receive a user inputactivating one or more destructive function control modes; receive auser selection of one or more destructive functions; enable the displayof a destructive function confirmation option; and upon receipt of auser selection of the destructive function confirmation option, performone or more actions on one or more physical rig components correspondingto the selected one or more destructive functions.
 6. The computingsystem of claim 5, where the one or more destructive functions compriseone or more of: a pipe cutting action; and a BOP disconnect action. 7.The computing system of claim 2, the one or more software applicationsbeing further configured to perform an audible feedback function, theaudible feedback function comprising providing an audible confirmationof the user selection before a function corresponding to the userselection is initiated.
 8. The computing system of claim 2, where theGUI comprises a single active interface window or a plurality of activeinterface windows and where the GUI displays: the action zone in acentral portion of the GUI; the interface control subzone on a rightside portion of the action zone; the information subzone in a centralportion of the action zone; and/or the system control subzone on a leftside portion of the action zone.
 9. The computing system of claim 2, theHMI application further configured to: enable a display of a colorpalette comprising a red color and a green color; display a red color toindicate one or more abnormal component states; and display a greencolor to indicate one or more of an error-free operating status and aphysical rig configuration having all rig components correctlyconfigured for a particular rig operation.
 10. The computing system ofclaim 9, where the one or more events comprise one or more of acomponent failure and an alarm.
 11. A method of implementing a humanmachine interface (HMI) application, the method comprising: initiating asession of the HMI application by receiving a user input on a userinterface running or stored on a hardware device comprising at least oneprocessor; enabling the display of a plurality of non-overlapping zonescomprising an action zone and one or more of: a high-level navigationzone comprising one or more selectable navigation options; or a systemheader zone; enabling the display of a plurality of selectable actionoptions in the action zone, the action zone comprising a plurality ofnon-overlapping subzones, the subzones comprising: an interface controlsubzone, an information subzone, and a system control subzone; enablingthe display of one or more selectable action options, the one or moreselectable action options being displayed in predesignated subzones,wherein the plurality of selectable action options is modified based ona selection of the one or more selectable navigation options; receiving,at the hardware device, data representing a user selection of one of theone or more selectable action options; and controlling an operatingstate of one or more physical offshore drilling rig components based onthe user selection.
 12. The method of claim 11, further comprisingimplementing one or more standard operating procedures applicable to oneor more offshore drilling rigs.
 13. The method of claim 12, furthercomprising: receiving, at the hardware device, data representing one ormore modifications to the one or more standard operating procedures;applying the one or more modifications to the one or more standardoperating procedures to create one or more modified standard operatingprocedures; and applying the one or more modified standard operatingprocedures to the one or more offshore drilling rigs.
 14. The method ofclaim 11, the one or more selectable navigation options comprising oneor more of: a blowout preventer (BOP) stack control option; adiagnostics option; a testing option; a settings option; an alarmsoption; a diverter option; a surface system option; an electronic riserangle option; or an emergency disconnect option.
 15. The method of claim14, further comprising, after receiving a user selection of the BOPstack control option: enabling the display of a layout diagramcomprising one or more selectable components in the information subzone,the layout diagram representing a current stack arrangement of the oneor more physical offshore drilling rig components; and enabling thedisplay of one or more control options in the interface control subzone,the one or more control options comprising one or more of: one or morecontrol procedures, or one or more destructive function control modes.16. The method of claim 11, further comprising: enabling the display ofone or more visual status displays in the system control subzone; andafter receiving a user selection of one of the selectable components orcontrol options, enabling the display of one or more function controloptions in the system control subzone, the one or more function controloptions corresponding to the user selection of one of the selectablecomponents or control options.
 17. The method of claim 16, furthercomprising: enabling the display of a flowpath within the layoutdiagram; enabling the display of one or more colors for the flowpath,the one or more highlighted colors corresponding to one or morepredicted flowpath states of the flowpath, wherein the one or morepredicted flowpath states comprise: a predicted fluid flow state; apredicted fluid non-flow state; or a predicted fluid pressure buildupstate. after receiving a user selection of one of the selectablecomponents or control options, enabling the display of one or morefunction control options in the system control subzone, the one or morefunction control options corresponding to the user selection of one ofthe selectable components or control options.
 18. The method of claim17, further comprising: receiving a user input activating one or moredestructive function control modes; receiving a user selection of one ormore destructive functions; enabling the display of a destructivefunction confirmation option; and upon receipt of a user selection ofthe destructive function confirmation option, performing one or moreactions on the one or more physical rig components corresponding to theselected one or more destructive functions.
 19. The method of claim 17,further comprising, after receipt of a user selection of one of theselectable components, control options, or destructive functionconfirmation option, performing an audible feedback function, theaudible feedback function comprising providing an audible confirmationof the user selection before a function corresponding to the userselection is initiated.
 20. The method of claim 19, where the one ormore destructive functions comprise one or more of: a pipe cuttingaction; or a BOP disconnect action.